# Convert PanelBuilder RIO applications

When a PanelBuilder 1400e or PanelBuilder32 RIO application is converted for use in FactoryTalk View Machine Edition on PanelView Plus or PanelView Plus CE platforms, some additional steps are required to make the application usable.

Tip: | FactoryTalk Linx new alias BitArray data type allows PanelView 1400e Binary and Byte tags that were previously unsupported, to be converted to RSLinx RIO aliases. If you have previously converted PanelBuilder RIO applications, you may want to convert them again to take advantage of this expanded support. Tags listed here continue to be unsupported. RIO communication is not presently supported for the Windows 7 SP1, Windows 10, Windows Server 2008 R2 SP1, Windows Server 2012, and Windows Server 2016 run time, or for test run. PanelView Plus 7 Standard applications and Compact Machine Edition applications do not support RIO.

## Convert an RIO application

As the Machine Edition Import Wizard processes an RIO application, the following changes are made:

- The RIO rack configuration is saved in an RIO XML file.
- The RIO block transfer file configuration is saved in the RIO XML file.
- Supported tags are converted to HMI device tags and saved as aliases in the RIO XML file.
- Unsupported tags are converted to HMI memory tags.
- Block tags assigned to a PanelBuilder 1400e Alarm Trigger are converted to direct references.
- I/O tag bit references are changed from octal to decimal.

## Additional steps

You will have to complete the following steps on the converted application:

- Delete the Pass-Through file assignment. FactoryTalk View Studio does not support pass-through file transfers.
- Make sure the block transfer file numbers are sequential without gaps. If necessary, renumber the block transfer file numbers so there are no missing numbers. Tag addresses in the application will change automatically to match the new number.
- Add an RIO driver in the FactoryTalk Linx data server.
- Create a device shortcut named PVRIO that points to the RIO data device.
- Import the RIO XML file created during the conversion into the RIO driver.
- Correct any invalid RIO configurations.
- Save the corrected RIO configuration.

## To make an imported RIO application run on Machine Edition

1. Open the imported application in FactoryTalk View Studio.
2. Open the FactoryTalk Linx data server and double-click Communications set up.
3. In the Communications Setup editor, add an RIO driver.
4. In the Communications Setup editor, expand the RIO entry to show RIO data.
5. Right-click RIO data and select Configure RIO to open the RIO Configuration dialog box.
6. Right-click RIO and then select Import.
7. Browse to the location of the RIO XML file created during the conversion and click OK.

   The XML file will be saved in the root of the project’s directory. For example, if you created an ME application with the name PV1 and imports a PanelBuilder application, the PV RIO XML file is in \Users\Public\Public Documents\RSView Enterprise\ME\HMI Projects\PV1.

8. Open the XML file and look for red "X" icons indicating invalid RIO configurations.
9. Correct the invalid RIO configurations and save the file.

## See also

Unsupported PanelBuilder 1400e RIO tags

Unsupported PanelBuilder32 RIO tags

Unsupported PanelBuilder32 Objects and Features